Experiments

In this lesson, we'll look at a few things you can do to experiment with the app.

We'll cover the following

Here are a few experiments you can try on the app:

  • Press the RUN button to start the example.

  • Disable JavaScript in the browser. Is the example still usable? Specifically, does the postbox integration still work?

  • Analyze the JavaScript code for transclusion at https://github.com/ewolff/crimson-styleguide/tree/master/components/preview. How difficult is it to replace this code with an implementation that uses a different JavaScript library? Try it in the live app below!

Try it yourself!#

Note: it might take a while for the app to set up.

/
docker-compose.yml
Your app can be found at: https://811lgmnxmw1xy.educative.run

Add your own microservice!#

Supplement the system with an additional microservice.

  • A microservice that generates a note for a meeting with a client can serve as an example.

  • Of course, to add the service you can copy and modify one of the existing Node.js or the Spring Boot microservice.

  • The microservice has to be accessible by the portal microservice. To achieve this, you have to integrate a link to the new microservice into the portal.

  • The link can provide the partner ID to the new microservice. This ID identifies the customer and might be useful in figuring out which customer the note belongs to.

  • After entering the note, the microservice can trigger a redirect back to the portal.

  • For a uniform look and feel, you have to use the assets from the style guide project. The Spring Boot project for the postbox shows the integration for Spring/Java and the portal for Node.js. Of course, you can also use other technologies for the implementation of the new microservice.

  • The microservice can store the data concerning the meeting in a separate database.

Try this in the live app above!

                                                 Q U I Z  

1

What is the purpose of the style guide project?

You may choose more than one answer.

A)

All microservices use this in order to maintain a uniform look and feel across the frontend.

B)

To guide all the frontend developers about coding conventions that must be maintained throughout the project.

C)

To keep visual consistency.

Question 1 of 20 attempted

In the next lesson, we’ll look at a conclusion to this chapter.

Variations
Introduction
Mark as Completed
Report an Issue